System and method for generating web sites in an arbitrary object framework

ABSTRACT

A method and system for generating a computer application is disclosed. The computer application is generated on a host system in an arbitrary object framework that separates a content of said computer application, a form of said computer application and a functionality of said computer application. Arbitrary objects are created with corresponding arbitrary names of various object types for generating said content of said computer application, said form of said computer application, and said functionality of said computer application. The arbitrary objects are managed in an object library. The arbitrary objects are deployed from said object library into a design framework to create said computer application.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 09/410,334, filed Oct. 1, 1999, now U.S. Pat. No. 6,826,744.

TECHNICAL FIELD OF THE INVENTION

This invention relates generally to systems and methods for generating software applications in an arbitrary object framework, and more specifically to systems and methods for generating web sites in an arbitrary object framework.

BACKGROUND OF THE INVENTION

Three processes used to create complex software applications such as web sites are form, function, and content. Form includes graphic designs, user interfaces, and graphical representations created by a designer or a group of designers. Function includes logical functionality, which can be software code created by a programmer or group of programmers. Form includes informative content. Informative content can include written, recorded, or illustrated documentation, such as photographs, illustrations, product marketing material, and news articles. Content can be created by writers, photographers, artists, reporters, or editors.

Currently, typical workflows dictate a serial approach to integrating the form, function, and content to create complex software applications such as a web site. The serial approach is illustrated in FIG. 1. In FIG. 1, content 10 for a complex software application can be chosen or created. Form 12 for the presentation of content 10 can then be created. Functionality 14 can then be generated using code to create the complex software application (product 16) with the desired information (content 10) and style (form 12). Using the method illustrated in FIG. 1, every final component of the complex software application must be manipulated by a programmer before it is ready to be used. The exact workflow may vary from industry to industry or business to business, but the basic restrictions are generally the same.

A traditional approach such as that illustrated in FIG. 1, may create unwanted bottlenecks in the production process. Each upstream revision, such as a change of content 10 or design 12, forces a repetition of the entire process. As an example, consider a web site for a large newspaper. The web site may have a function that can include a file into the web site. The marketing department may decide to change the appearance of the header on the web site depending on the browser of a user. In this case, a programmer may need to invoke an external script or embed some specific logic within the web site. Unfortunately, if there is a large web site with thousands of pages of information stored on a server, the programmer may have to change every one of the thousands of pages. Therefore, a small change by the marketing department can cause a large burden on the programming department.

Prior art solutions have succeeded in partially separating some of these functions. Notably, content management databases and digital repositories provide a means of separating content from form and function. Likewise, sophisticated software development teams frequently employ internal code structuring techniques that can help to minimize dependencies between interface designs and the functions they access. However, content management tools typically fail to address form/function issues. Therefore, there can still be production slow-downs due to changes in form that require a subsequent change in functionality.

SUMMARY OF THE INVENTION

Therefore a need exists for a method of generating complex software applications that reduces or eliminates production delays and the workload for programmers due to changes in content and/or form. This method should separate form, content and function so that each area can be independently changed.

The present invention provides a system and method for generating software applications that substantially eliminates or reduces disadvantages and problems associated with previously developed systems and methods used for generation of software applications. More specifically, the present invention provides a method for generating software applications in an arbitrary object framework. The method of the present invention separates content, form, and function of the computer application so that each may be accessed or modified independently. The method of this invention includes creating arbitrary objects, managing the arbitrary objects throughout their life cycle, and deploying the arbitrary objects in a design framework for use in complex computer applications.

The present invention provides an important technical advantage in that content, form, and function are separated from each other in the generation of the software application. Therefore, changes in design or content do not require the intervention of a programmer. This advantage decreases the time needed to change various aspects of the software application. Consequently, cost is reduced and versatility is increased.

The present invention provides another technical advantage in that users are not required to use a proprietary language to encode. These arbitrary objects may include encapsulated legacy data, legacy systems and custom programming logic from essentially any source in which they may reside. Any language supported by the host system, or any language that can be interfaced to by the host system, can be used to generate an object within the application.

The present invention provides yet another technical advantage in that it can provide a single point of administrative authority that can reduce security risks. For instance, a large team of programmers can work on developing a large group of arbitrary objects within the object library. If one object has a security hole, an administrator can enter the object library and disable that arbitrary object.

Still another technical advantage of the present invention is that it enables syndication of the software application. As noted above, functionality is separate from form and content. Consequently, a user can easily introduce a new look for the application or syndicate the content and functionality of the application to another group without having to recode all of the objects needed to access content.

Another technical advantage of the present invention is that it allows for personalization and profiling. With personalization, the web presentation is tailored to the specific needs of the web user based on the user's past history. Profiling also enables tailoring a web site or presentation. Profiling is dependent on environmental variables such as browser type or IP address.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present invention and the advantages thereof may be acquired by referring to the following description, taken in conjunction with the accompanying drawings in which like reference numbers indicate like features and wherein:

FIG. 1 illustrates a prior art workflow diagram for generating a software product;

FIG. 2 is a hierarchical workflow diagram for one embodiment of the present invention;

FIG. 3 is a flow diagram for one embodiment of the present invention;

FIG. 4 is a flow diagram for another embodiment of the present invention; and

FIG. 5 is a diagram illustrating the components of one environment of the present invention used to generate web sites.

DETAILED DESCRIPTION OF THE INVENTION

Preferred embodiments of the present invention are illustrated in the FIGUREs, like numerals being used to refer to like and corresponding parts of various drawings.

The present invention provides a system and method for using a hierarchical, arbitrary object framework for generating software applications. The method separates content, form, and function of the software application so that each can be accessed or modified independently. The method of this invention includes creating arbitrary objects, managing the arbitrary objects in an object library, and deploying the arbitrary objects in a design framework for use in computer applications.

FIG. 2 is a hierarchical workflow diagram for the present invention. Product 16 includes three contributing groups: content 10, form 12, and functionality 14. Content 10 can include written, recorded, or illustrated collateral such as documentation, photographic illustrations, product marketing material, and articles. Form 12 can include graphic designs such as user interfaces and graphical presentations. Function 14 can include the logical functionality of software code and scripts. The hierarchical framework separates content 10, form 12, and functionality 14 to generate product 16. Product 16 may be a computer software application such as a web site. Since content 10, design 12, and functionality 14 are separate entities independent of each other, modification in one group does not require corresponding modifications in another group. Each group can contribute to product 16 directly.

FIG. 3 is a flow diagram of one embodiment of the present invention. At step 20, arbitrary objects can be generated. Arbitrary objects may include any combination of application logic and data desired by a developer. Arbitrary objects can include text file pointers, binary file pointers, compiled executables, scripts, data base queries, shell commands, remote procedure calls, global variables, and local variables. The arbitrary object framework allows arbitrary objects to be referenced in a consistent manner regardless of the type. Also, the arbitrary object framework allows local arbitrary objects to either override global parent arbitrary objects or inherit capabilities and data from the global parent, regardless of the type of the local arbitrary object.

At step 22, these arbitrary objects can be managed in an object library. The life cycle of these objects may be managed in a consistent manner using revision tracking, roll back, and sign off. At step 24, objects can be deployed from the object library into a design framework to create the software application. Because the object pointers are not tied in any way to the functionality of the object, an object of one type can be easily replaced with another object of another type. This eliminates a common problem in content management systems of the inability to preview content within its appropriate location on the site or within the system. Normally, a special system made for the purpose of previewing a piece of content would have to be hard-coded to view the current approved live content for all other pieces except the piece in question. This multiplies the design problem, because changes in the design in the main site change all previous templates. In the method of the present invention, since all that exists within the framework is an arbitrary object, the arbitrary object can be swapped for another object that pulls the current piece content in question.

Using one embodiment of this invention, for example, the Features or Editorials page of a newspaper can be dynamically replaced. The present invention can execute all the normal objects that can be placed on the page to show the content as it would appear, and then take the one piece in question and replace it with a second object to be examined. Objects may be deployed globally across an entire system or locally within a specific area or sub-areas of a system.

FIG. 4 represents a flow diagram of another embodiment of the present invention. At step 30, arbitrary objects can be generated. At step 32, the arbitrary objects can be managed in an object library. Arbitrary objects can be deployed in a container page at step 34 to generate a web site.

Arbitrary objects may include any combination of application logic and data desired by a developer. Arbitrary objects can include text file pointers, binary file pointers, compiled executable scripts, database queries, shell commands, remote call procedures, global variables and local variables. Arbitrary objects may also include cached data queries and executables. The arbitrary object framework allows arbitrary objects to be referenced in a consistent manner regardless of the type of object. Also, the arbitrary object framework allows local arbitrary objects to either override global parent arbitrary objects or inherit capabilities and data from the global parent arbitrary object.

Arbitrary objects can execute any function that can be run or understood by the host computer system so that any underlying functionality of the operating system used by the host system can be defined as an object within the arbitrary framework. Legacy data, document objects, CGI programs, and database queries can all be encapsulated as objects within the arbitrary framework. The arbitrary object can be accessed by an arbitrary object name. Arbitrary objects are not tied to their functionality. One arbitrary object can be easily replaced with another arbitrary object of another type.

Arbitrary objects can be managed in an object library. The life cycle of the arbitrary objects may be managed in a consistent manner using revision tracking, roll-back, and sign-off. The object library can include separate specialized object libraries that can be administered separately by different developers in each area. For instance, for a web site used to generate a newspaper, there may be an advertising object library that is physically distinguished from other object libraries, such as an object library for sports or an object library for news. Therefore, queries for advertising can be created without impacting any other area of the web site.

Arbitrary objects can be deployed from the object library into a container page to generate the web site. The container page is a truly dynamic page. Unlike prior art methods, where a static copy of information is often pushed over a firewall to a live web site, the present invention incorporates object caching. An arbitrary object can be cached, rather than caching an entire page. When the arbitrary object is cached, certain elements of the arbitrary object can be specified as dynamic elements while others can be specified as static elements. Therefore, a web site can contain multiple dynamic web pages wherein objects used to construct the form, function, and content of the web page can contain dynamic elements and static elements. This provides flexibility for what needs to be computed or processed at the time that someone, such as a web user, accesses the web page.

FIG. 5 shows the components of one environment of the present invention used to generate web sites. A user with web browser 40 can connect to web server 44 through internet or intranet 42. Web server 44 can access static HTML web documents 46 as well as dynamic HTML documents 52. Dynamic HTML web documents 52 can be created using WebOS Object Manager 50. Dynamic HTML Web document 52 can include document objects 56, shell scripts 58, CGI programs 60, and database queries 62. Document objects 56, shell scripts 58, CGI programs 60, and database queries 62 can be stored in WebOS object library 54. Database queries 62 can result from extracting information from WebOS Information Database 68 and inputting the information into Dynamic HTML Web Template 66.

User Profile and Password Database 70 can provide web sites or systems with a means to take advantage of customer profiles to look at customer preferences or history, and dynamically replace a website object with another object that contains content information matching the user profile or preferences. Thus, the web site or system can dynamically allocate the correct content for a customer. This is important in commerce applications. A customer's buying history can be examined for trend items and the customer presented products that match his or her profile. Present personalization systems are written purely in custom code and require an inordinately large amount of time to construct the custom applications necessary to interpret the preferences of an individual user.

The method of present invention can perform object caching. This means that an object can be cached instead of caching an entire page. Object caching permits specifying elements of an object to be dynamic and elements of the object to be static. A system user can thus have the flexibility of specifying what needs to be computed or processed at the time a user accesses the system versus trying to anticipate and calculate in advance and cache and post the object over to a server.

Many functions are stored within an object library on an arbitrary object framework such that those functions can be accessed by name arbitrarily. This is in contrast to a traditional model where the function must be explicitly invoked with all its parameters included. Objects may execute any function that can be run or understood by the host computer system so that any underlying functionality of the host's operating system can be defined as an object within the framework of the method of the present invention. The object library can contain legacy data, document objects, CGI programs, and/or database queries, that can all be encapsulated as objects within a framework and accessed from within a design. All that is needed is the name of the function in order to access the function.

Objects can be controlled to perform functions based on a profile of an individual and environmental variables, such as the type of browser, the country of the individual or the individual's IP address. A specific competitor may be blocked from seeing certain objects on a web page created using the method of the present invention.

A critical distinction between the present invention and previous object oriented development systems is the need to know how a function can be called and what to expect it to return, rather than just knowing the function's name. This means that typically the system administrator calls the name of an object and passes parameters to the object. Any and all variable information or environmental information can be available to every object. The environment space can be available to all objects executed and an object can arbitrarily take advantage of any of the environmental information, depending on the design of the object.

Different areas of a web site can be administered separately by different developers in each of these areas. An advertising object library can be physically distinguished from other object libraries, such as those for sports and news. An advertising programmer can create new queries for the advertising section of a site without having to worry about affecting other areas of the site.

The present invention allows different object types to be interchangeable. The object name is essentially just another variable in the environment. Also different variables can also be interchangeable. The object framework can be designed such that objects and variables can be kept in the same name space, every object can have access to all the environmental settings, and every object pointer can potentially be another name in the name space.

Object caching, rather than page caching can be implemented with the present invention. These objects can be stored in an object library. An object in the object library can be a file, a global variable, an executable script, a database query, a cached executable or a cached database query. This means that the results of a query can be stored in a static file using the object name as long as the static file has not expired. This is important if the query is a lengthy query.

A technical advantage of the present invention is that it allows for syndication. Syndication enables the content and function of a particular web site to be syndicated to another web site or web presentation. For instance, if a company would like to roll out a new look or syndicate its content and functionality to another business, this can be easily accomplished using the present invention. Since there is no application code resident in a web page itself, the same data can be repackaged in a number of different ways across multiple sites. There is no need to recode the design elements or design pages on the web site or recode any functions that are needed to access the content of the website. The present invention enables electronic store fronts to sell from a single source with a unique interface design. Also, newspaper chains can distribute international and national content from a single source and add local content themselves.

Another technical advantage of the present invention is that it allows for a single point of control when developing a web site. Therefore, if a large team of developers are working on a site, and multiple persons are contributing arbitrary objects to the overall arbitrary framework, then if one of the arbitrary objects has a security hole in it, the arbitrary object can be easily accessed in the object library and disabled. This security feature can immediately shut down that function across the entire web site and patch the security hole.

The present invention provides still another technical advantage in that it allows for personalization. Personalization enables companies that want to take advantage of a customer profile to look at the customer's preferences or histories and deploy information to the web site specific to the customer.

Another technical advantage of the present invention allows for profiling. Profiling enables control over the arbitrary objects presented in a web site based on a profile of the individual accessing the web site. Profiling entails determining different environmental variables such as the type of browser hitting the site, the country of the individual accessing the site, and/or the individual's IP address. This can enable a company to present specific information to the individual based on the individual's environmental variables.

Although the present invention has been described in detail herein with reference to the illustrative embodiments, it should be understood that the description is by way of example only and is not to be construed in a limiting sense. It is to be further understood, therefore, that numerous changes in the details of the embodiments of this invention and additional embodiments of this invention will be apparent to, and may be made by, persons of ordinary skill in the art having reference to this description. It is contemplated that all such changes and additional embodiments are within the spirit and true scope of this invention as claimed below. 

1. A system for generating a computer application on a host system in an arbitrary object framework that separates a content of said computer application, a form of said computer application, and a functionality of said computer application, said system including a computer comprising a processor and a memory operably coupled to said processor, said memory being configured for storing a computer program executable by said processor, said computer program comprising: a first set of executable instructions for creating arbitrary objects with corresponding arbitrary names of content objects used in generating said content of said computer application, form objects used in defining said form of said computer application, and function objects used in executing said functionality of said computer application each arbitrary object being separate from each other arbitrary object; a second set of executable instructions for managing said arbitrary objects in an arbitrary object library; and a third set of executable instructions for deploying said arbitrary objects from said arbitrary object library into a design framework to create said computer application.
 2. The system of claim 1, wherein said computer application is a web site.
 3. The system of claim 1, wherein each of said various object types include a type selected from the group consisting of: text file pointers; binary file pointers; compiled executables; shell commands; remote procedure calls; global variables; cached executables; cached database queries; local variables; and local objects and global parent objects, wherein said local objects are capable of overriding said global parent objects, and wherein said local objects are capable of inheriting data from said global parent objects.
 4. The system of claim 1, wherein the third set of executable instructions are for deploying arbitrary objects locally.
 5. The system of claim 1, wherein the second set of executable instructions for managing said arbitrary objects further comprises executable instructions for revision tracking.
 6. The system of claim 1, wherein the second set of executable instructions for managing said arbitrary objects further comprises executable instructions for using rollback.
 7. The system of claim 1, wherein the second set of executable instructions for managing said arbitrary objects further comprises executable instructions for using signoff.
 8. The system of claim 1, wherein the third set of exectable instructions include instructions to access and deploy arbitrary objects into said design framework using said corresponding arbitrary names.
 9. The system of claim 1, further comprising executable instructions for swapping an arbitrary object of one type with an arbitrary object of another type.
 10. The system of claim 1, further comprising executable instructions for caching objects.
 11. The system of claim 10, wherein the executable instructions for caching objects further comprises exectable instructions for specifying some elements of an arbitrary object to be dynamic elements and specifying some elements of said arbitrary object to be static elements.
 12. The system of claim 1, further comprising executable instructions for generating arbitrary objects in a programming language that is compatible and supported by said host system.
 13. A system for generating a web site on a host system in an arbitrary object framework that separates a content of said web site, a form of said web site, and a functionality of said web site, said system including a computer comprising a processor and a memory operably coupled to said processor, said memory being configured for storing a computer program executable by said processor, said computer program comprising: a first set of executable instructions for creating arbitrary objects with corresponding arbitrary names of content objects used in generating said content of said web site, form objects used in defining said form of said web site, and function objects used in executing said functionality of said web site, each arbitrary object being separate from each other arbitrary object; a second set of executable instructions for managing said arbitrary objects in an arbitrary object library; and a third set of executable instructions for deploying said arbitrary objects from said arbitrary object library to a container page to create said web site.
 14. The system of claim 13, wherein each of said various object types include a type selected from the group consisting of: text file pointers; binary file pointers; compiled executables; shell commands; remote procedure calls; global variables; cached executables; cached database queries; local variables; and local objects and global parent objects, wherein said local objects are capable of overriding said global parent objects, and wherein said local objects are capable of inheriting data from said global parent objects.
 15. The system of claim 13, wherein the third set of executable instructions are for deploying arbitrary objects locally.
 16. The system of claim 13, wherein the second set of executable instructions for managing said arbitrary objects further comprises executable instructions for revision tracking.
 17. The system of claim 13, wherein the second set of executable instructions for managing said arbitrary objects further comprises executable instructions for using rollback.
 18. The system of claim 13, wherein the second set of executable instructions for managing said arbitrary objects further comprises executable instructions for using signoff.
 19. The system of claim 13, wherein the third set of executable instructions include instructions to access and deploy arbitrary objects into said design framework using said corresponding arbitrary names.
 20. The system of claim 19, wherein the third set of executable instructions is capable of accessing and deploying the arbitrary objects into said container page using said corresponding arbitrary names.
 21. A system for generating a computer application on a host system in an arbitrary object framework that separates a content of said computer application, a form of said computer application, and a functionality of said computer application, said system including a computer comprising a processor and a memory operably coupled to said processor, said memory being configured for storing a computer program executable by said processor, said computer program comprising: a first set of executable instructions for creating arbitrary objects with corresponding arbitrary names of content objects used in generating said content of said computer application, form objects used in defining said form of said computer application, and function objects used in executing said functionality of said computer application, each arbitrary object being callable by name only, each arbitrary object being independently modifiable without corresponding modifications being made to any other arbitrary object, and each arbitrary object further being interchangable with other arbitrary objects; a second set of executable instructions for managing said arbitrary objects in an arbitrary object library; and a third set of executable instructions for deploying said arbitrary objects from said arbitrary object library into a design framework to create said computer application.
 22. The system of claim 21, wherein said computer application is a web site.
 23. The system of claim 21, wherein each of said various object types include a type selected from the group consisting of: text file pointers; binary file pointers; compiled executables; shell commands; remote procedure calls; global variables; cached executables; cached database queries; local variables; and local objects and global parent objects, wherein said local objects are capable of overriding said global parent objects, and wherein said local objects are capable of inheriting data from said global parent objects.
 24. The system of claim 21, wherein the third set of executable instructions are for deploying arbitrary objects locally.
 25. The system of claim 21, wherein the second set of executable instructions for managing said arbitrary objects further comprises executable instructions for revision tracking.
 26. The system of claim 21, wherein the second set of executable instructions for managing said arbitrary objects further comprises executable instructions for using rollback.
 27. The system of claim 21, wherein the second set of executable instructions for managing said arbitrary objects further comprises executable instructions for using signoff.
 28. The system of claim 21, wherein the third set of exectable instructions include instructions to access and deploy arbitrary objects into said design framework using said corresponding arbitrary names.
 29. The system of claim 21, further comprising executable instructions for swapping an arbitrary object of one type with an arbitrary object of another type.
 30. The system of claim 21, further comprising executable instructions for caching objects.
 31. The system of claim 30, wherein the executable instructions for caching objects further comprises exectable instructions for specifying some elements of an arbitrary object to be dynamic elements and specifying some elements of said arbitrary object to be static elements.
 32. The system of claim 21, further comprising executable instructions for generating arbitrary objects in a programming language that is compatible and supported by said host system. 